This, the second release of this resource, is offered with my apologies to all who got ahold of the previous one. In my development efforts, I had added a remapping of the "s" key to an "e" under certain conditions for testing. That was the version that got inadvertently uploaded. Here is the corrected one.
-----
November 1, 1992
You can fix your Apple VT102 Communication Toolbox Terminal tool to work properly with a powerbook keyboard by using the enclosed "kbd2" resource to replace the one in the VT102 tool (using ResEdit). This definately works on the 1.0.2 version of VT102. I have not tried it on earlier versions, but I think it will work on any. I also believe this will fix the VT320 tool, although I have not tried that either.
Start with a fresh copy of the VT102 tool... The small hack (7008 4E71) I posted earlier to fix the arrow keys only is not needed for this fix to work.
This new resource has four effects:
1. Fixes the arrow keys, which otherwise send the wrong codes on a Powerbook.
2. Makes it possible to type the keypad keys without using the pull-down menu by using the option key plus the same key as on the keypad. For example, typing Option-Comma sends the appropriate code for the keypad comma key.
3. Makes it possible to type the keypad function keys without using the pull-down menu by using the Control key plus the number keys 1 to 4. For example, Control-1 send the appropriate code for the keypad PF1 key.
4. Makes Control-` (grave accent) send a null (character 0). This is because Control-2 used to send a null and I wiped that out implementing the function keys in item 3.
This should fix the VT102 tool in a universal manner such that these functions will work on any keyboard or machine. I have only tried it on my PowerBook 140. I welcome feedback on your results on other machines.
This fix is ideaware. If you use it, please send me an idea for a nifty utility program I can write (preferably for the PowerBook!). If you don't have an idea, please just send a note to let me know what kind of machine you have and whether this fixed it or not!
